Minor precision fix on unproject #1471
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi! I found a minor issue inside the code sample given for the
unproject
insideCameraBase
.The provided code block returns
True
as expected only when the camera is set without any RotationR
or TransformationT
.An example is given below:
I at first thought that
R
andT
were not being considered during unprojection, only to realize afterwards that the print statement above in this case returnsFalse
due to precision error.Changing this line by increasing the absolute threshold
atol
as also done in the unit tests solves the issue:pytorch3d/tests/test_cameras.py
Line 619 in d388881
Thanks a lot!